Performance assessment device for evaluating a performance of a building management system

ABSTRACT

A performance assessment device for evaluating a building management system (BMS). The device includes a communication interface. The communication interface is configured to communicate with a BMS network, the BMS network in communication with the BMS. The device further includes a processing circuit. The processing circuit is configured to receive data related to the BMS via the communication interface. The processing circuit is further configured to evaluate the received BMS data to generate a current status of the BMS inventory, and to further generate an assessment of the BMS performance. The assessment of the BMS performance includes one or more performance metrics associated with the performance of the BMS.

BACKGROUND

The present disclosure relates generally to building management systems.The present disclosure relates more particularly to systems and methodsfor presenting data, and changes to control strategies, associated witha building management systems (BMS).

A building management system (BMS) is, in general, a system of devicesconfigured to control, monitor, and manage equipment in or around abuilding or building area. A BMS can include a heating, ventilation, andair conditioning (HVAC) system, a security system, a lighting system, afire alerting system, another system that is capable of managingbuilding functions or devices, or any combination thereof. BMS devicesmay be installed in any environment (e.g., an indoor area or an outdoorarea) and the environment may include any number of buildings, spaces,zones, rooms, or areas. A BMS may include a variety of devices (e.g.,HVAC devices, controllers, chillers, fans, sensors, etc.) configured tofacilitate monitoring and controlling the building space. Throughoutthis disclosure, such devices are referred to as BMS devices or buildingequipment.

Currently, many building management systems provide control of an entirefacility, building, or other environment. The building management systemmay control HVAC systems, water system, lights, air quality, security,and/or any other aspect of the facility within the purview of thebuilding management system. These systems may require skilled persons toadjust, control, and otherwise operate the building management system,due to the complexity. In large facilities or buildings, this managementcan be labor intensive. Moreover, in buildings where dynamic managementof the building management system is required (i.e. buildings withmultiple independent HVAC requirements), advanced control strategies maybe required along with ongoing preventative maintenance of individualsystems within the building management system to adjust for the dynamicuse of the building or facility.

Once a BMS system is commissioned and operational at a user site, thegenerally large size of BMS systems makes verification and assessment ofthe system's performance difficult. Obtaining performance informationregarding the BMS system can be critical in determining if the BMSsystem is functioning as per its specified design. This information mayprovide useful insights into the BMS system, such as opportunities forfunction or performance enhancements. Furthermore, as systems changeover time, it is important to monitor and understand how the changes tothe BMS system over time have affected the BMS system. For example, asadditional devices and data points are added to a BMS system, theoverall system performance should be monitored to determine the impactof the changes to the BMS system. Thus, it would be desirous to have atool available that could easily and efficiently analyze a BMS system,in part or in whole, to evaluate a number of performance metrics, andprovide suggestions relating to the optimization of the BMS system.

Furthermore, BMS systems are often modified with new features or devicesover time. However, due to the large number of data points, it may bedifficult to monitor the changes to the BMS system. Additionally, theperformance changes in the BMS due to the modification and or additionof devices and features is also difficult to quickly and easilydetermine. Providing a comparison of a current performance and inventoryof a BMS against the performance and inventory of a BMS from a pastpoint in time may allow a user to see changes in the BMS system overperiods of time. This can provide a powerful tracking tool that can beused by a user to evaluate a BMS over time.

Additionally, many BMS system do not fully utilize all of the availablefeatures. In some instances, a user may avoid utilizing some featuresdue to perceived complexity or cost. In other examples, new features maybe developed for use with a BMS after the initial commissioning iscomplete. These features may provide powerful tools to a user of theBMS. For example, the features may provide energy and/or cost savings,increase efficiencies, decrease waste and emissions, or generallyprovide other benefits to the BMS. Accordingly, it would be desirous tohave a tool that could provide verification of a BMS system, performcomparisons of devices, features and performance over time, and providean assessment of the utilization of certain features available withinthe BMS.

SUMMARY

One implementation of the present disclosure is a performance assessmentdevice for evaluating a building management system (BMS). The deviceincludes a communication interface. The communication interface isconfigured to communicate with a BMS network, the BMS network incommunication with the BMS. The device further includes a processingcircuit. The processing circuit is configured to receive data related tothe BMS via the communication interface. The processing circuit isfurther configured to evaluate the received BMS data to generate acurrent status of the BMS inventory, and to further generate anassessment of the BMS performance. The assessment of the BMS performanceincludes one or more performance metrics associated with the performanceof the BMS.

A further implementation of the present disclosure is a method forassessing the performance of a building management system using aperformance assessment tool. The method includes scanning the BMS toretrieve one or more attributes associated with the BMS. The methodfurther includes determining performance data for one or moreperformance aspects of the BMS based on the retrieved attributesassociated with the BMS, and accessing a knowledgebase, via acommunicating interface of the performance assessment tool, to retrievea plurality of performance analysis data. The method also includesanalyzing the performance data to determine one or more performancemetrics associated with the performance aspects of the BMS based on theretrieved performance analysis data.

A further implementation of the present disclosure is a performanceassessment device for evaluating a performance of a building managementsystem (BMS). The device includes a first communication interfaceconfigured to communicate with a BMS network, the BMS network incommunication with the BMS. The device also includes a secondcommunication interface configured to communicate with a knowledgebase.The device further includes a processing circuit configured to receivedata related to the BMS via the first communication interface, andperformance analysis data from the knowledgebase via the secondcommunication interface. The processing circuit is further configured toevaluate the received BMS data to generate a current assessment of oneor more performance aspects of the BMS based on the received data fromthe BMS and the received performance analysis data from theknowledgebase.

Those skilled in the art will appreciate that the summary isillustrative only and is not intended to be in any way limiting. Otheraspects, inventive features, and advantages of the devices and/orprocesses described herein, as defined solely by the claims, will becomeapparent in the detailed description set forth herein and taken inconjunction with the accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a drawing of a building equipped with a building managementsystem (BMS) and a HVAC system, according to some embodiments.

FIG. 2 is a schematic of a waterside system which can be used as part ofthe HVAC system of FIG. 1, according to some embodiments.

FIG. 3 is a block diagram of an airside system which can be used as partof the HVAC system of FIG. 1, according to some embodiments.

FIG. 4 is a block diagram of a BMS which can be used in the building ofFIG. 1, according to some embodiments.

FIG. 5 is a block diagram illustrating a performance assessment tool,according to some embodiments.

FIG. 6 is a flow chart illustrating a licensing process for aperformance assessment tool, according to some embodiments.

FIG. 7 is a flow chart illustrating a system inventorying process,according to some embodiments.

FIG. 8 is a screenshot illustrating a dialog box for generating a newinventory project, according to some embodiments.

FIG. 9 is a screenshot illustrating a file comparison interface,according to some embodiments.

FIG. 10 is a screen shot illustrating an example inventorying report,according to some embodiments.

FIG. 11 is a screenshot illustrating an example inventory comparisonreport, according to some embodiments.

FIG. 12 is a screenshot illustrating a comparison summary report,according to some embodiments.

FIG. 13A is a flow chart illustrating a system performance assessmentprocess, according to some embodiments.

FIG. 13B is a flow chart illustrating a system performance comparisonprocess, according to some embodiments.

FIG. 14 is a screen shot illustrating a performance assessment summary,according to some embodiments.

FIG. 15 is a screen shot illustrating a supervisory device performanceassessment summary, according to some embodiments.

FIG. 16 is a screen shot illustrating a controller performanceassessment summary, according to some embodiments.

FIG. 17 is a screen shot illustrating a point summary, according to someembodiments.

FIG. 18 is a screen shot illustrating a performance and savings report,according to some embodiments.

FIG. 19 is a screen shot illustrating a maintenance and reliabilityreport, according to some embodiments.

FIG. 20 is a screen shot illustrating a security and standards report,according to some embodiments.

FIG. 21 is a screen shot illustrating a detailed scheduling report,according to some embodiments.

FIG. 22 is a screen shot illustrating a detailed motor report, accordingto some embodiments.

FIG. 23 is a screen shot illustrating an air handling unit resetstrategies report, according to some embodiments.

FIG. 24 is a screen shot illustrating a 100% outdoor air handling unitreport, according to some embodiments.

FIG. 25 is a screen shot illustrating a dirty filter report, accordingto some embodiments.

FIG. 26 is a screen shot illustrating a detailed UL listed devicereport, according to some embodiments.

FIG. 27 is a screen shot illustrating a detailed firmwarevulnerabilities report, according to some embodiments.

FIG. 28 is a screen shot illustrating a detailed economizer report,according to some embodiments.

FIG. 29 is a screen shot illustrating a performance comparison report,according to some embodiments.

FIG. 30 is a flow chart illustrating a feature assessment process,according to some embodiments.

FIG. 31 is a screen shot illustrating an optimal start feature report,according to some embodiments.

FIG. 32 is a screen shot illustrating a demand limiting load rollingfeature report, according to some embodiments.

FIG. 33 is a screen shot illustrating a user views report, according tosome embodiments.

FIG. 34 is a flow chart illustrating a riser assessment process,according to some embodiments.

DETAILED DESCRIPTION

Building Management System and HVAC System

Referring now to FIGS. 1-4, an exemplary building management system(BMS) and HVAC system in which the systems and methods of the presentdisclosure can be implemented are shown, according to an exemplaryembodiment. Referring particularly to FIG. 1, a perspective view of abuilding 10 is shown. Building 10 is served by a BMS. A BMS is, ingeneral, a system of devices configured to control, monitor, and manageequipment in or around a building or building area. A BMS can include,for example, a HVAC system, a security system, a lighting system, a firealerting system, any other system that is capable of managing buildingfunctions or devices, or any combination thereof.

The BMS that serves building 10 includes an HVAC system 100. HVAC system100 can include a plurality of HVAC devices (e.g., heaters, chillers,air handling units, pumps, fans, thermal energy storage, etc.)configured to provide heating, cooling, ventilation, or other servicesfor building 10. For example, HVAC system 100 is shown to include awaterside system 120 and an airside system 130. Waterside system 120 canprovide a heated or chilled fluid to an air handling unit of airsidesystem 130. Airside system 130 can use the heated or chilled fluid toheat or cool an airflow provided to building 10. An exemplary watersidesystem and airside system which can be used in HVAC system 100 aredescribed in greater detail with reference to FIGS. 2-3.

HVAC system 100 is shown to include a chiller 102, a boiler 104, and arooftop air handling unit (AHU) 106. Waterside system 120 can use boiler104 and chiller 102 to heat or cool a working fluid (e.g., water,glycol, etc.) and can circulate the working fluid to AHU 106. In variousembodiments, the HVAC devices of waterside system 120 can be located inor around building 10 (as shown in FIG. 1) or at an offsite locationsuch as a central plant (e.g., a chiller plant, a steam plant, a heatplant, etc.). The working fluid can be heated in boiler 104 or cooled inchiller 102, depending on whether heating or cooling is required inbuilding 10. Boiler 104 can add heat to the circulated fluid, forexample, by burning a combustible material (e.g., natural gas) or usingan electric heating element. Chiller 102 can place the circulated fluidin a heat exchange relationship with another fluid (e.g., a refrigerant)in a heat exchanger (e.g., an evaporator) to absorb heat from thecirculated fluid. The working fluid from chiller 102 and/or boiler 104can be transported to AHU 106 via piping 108.

AHU 106 can place the working fluid in a heat exchange relationship withan airflow passing through AHU 106 (e.g., via one or more stages ofcooling coils and/or heating coils). The airflow can be, for example,outside air, return air from within building 10, or a combination ofboth. AHU 106 can transfer heat between the airflow and the workingfluid to provide heating or cooling for the airflow. For example, AHU106 can include one or more fans or blowers configured to pass theairflow over or through a heat exchanger containing the working fluid.The working fluid can then return to chiller 102 or boiler 104 viapiping 110.

Airside system 130 can deliver the airflow supplied by AHU 106 (i.e.,the supply airflow) to building 10 via air supply ducts 112 and canprovide return air from building 10 to AHU 106 via air return ducts 114.In some embodiments, airside system 130 includes multiple variable airvolume (VAV) units 116. For example, airside system 130 is shown toinclude a separate VAV unit 116 on each floor or zone of building 10.VAV units 116 can include dampers or other flow control elements thatcan be operated to control an amount of the supply airflow provided toindividual zones of building 10. In other embodiments, airside system130 delivers the supply airflow into one or more zones of building 10(e.g., via supply ducts 112) without using intermediate VAV units 116 orother flow control elements. AHU 106 can include various sensors (e.g.,temperature sensors, pressure sensors, etc.) configured to measureattributes of the supply airflow. AHU 106 can receive input from sensorslocated within AHU 106 and/or within the building zone and can adjustthe flow rate, temperature, or other attributes of the supply airflowthrough AHU 106 to achieve set-point conditions for the building zone.

Referring now to FIG. 2, a block diagram of a waterside system 200 isshown, according to an exemplary embodiment. In various embodiments,waterside system 200 can supplement or replace waterside system 120 inHVAC system 100 or can be implemented separate from HVAC system 100.When implemented in HVAC system 100, waterside system 200 can include asubset of the HVAC devices in HVAC system 100 (e.g., boiler 104, chiller102, pumps, valves, etc.) and can operate to supply a heated or chilledfluid to AHU 106. The HVAC devices of waterside system 200 can belocated within building 10 (e.g., as components of waterside system 120)or at an offsite location such as a central plant.

In FIG. 2, waterside system 200 is shown as a central plant having aplurality of subplants 202-212. Subplants 202-212 are shown to include aheater subplant 202, a heat recovery chiller subplant 204, a chillersubplant 206, a cooling tower subplant 208, a hot thermal energy storage(TES) subplant 210, and a cold thermal energy storage (TES) subplant212. Subplants 202-212 consume resources (e.g., water, natural gas,electricity, etc.) from utilities to serve the thermal energy loads(e.g., hot water, cold water, heating, cooling, etc.) of a building orcampus. For example, heater subplant 202 can be configured to heat waterin a hot water loop 214 that circulates the hot water between heatersubplant 202 and building 10. Chiller subplant 206 can be configured tochill water in a cold water loop 216 that circulates the cold waterbetween chiller subplant 206 building 10. Heat recovery chiller subplant204 can be configured to transfer heat from cold water loop 216 to hotwater loop 214 to provide additional heating for the hot water andadditional cooling for the cold water. Condenser water loop 218 canabsorb heat from the cold water in chiller subplant 206 and reject theabsorbed heat in cooling tower subplant 208 or transfer the absorbedheat to hot water loop 214. Hot TES subplant 210 and cold TES subplant212 can store hot and cold thermal energy, respectively, for subsequentuse.

Hot water loop 214 and cold water loop 216 can deliver the heated and/orchilled water to air handlers located on the rooftop of building 10(e.g., AHU 106) or to individual floors or zones of building 10 (e.g.,VAV units 116). The air handlers push air past heat exchangers (e.g.,heating coils or cooling coils) through which the water flows to provideheating or cooling for the air. The heated or cooled air can bedelivered to individual zones of building 10 to serve the thermal energyloads of building 10. The water then returns to subplants 202-212 toreceive further heating or cooling.

Although subplants 202-212 are shown and described as heating andcooling water for circulation to a building, it is understood that anyother type of working fluid (e.g., glycol, CO2, etc.) can be used inplace of or in addition to water to serve the thermal energy loads. Inother embodiments, subplants 202-212 can provide heating and/or coolingdirectly to the building or campus without requiring an intermediateheat transfer fluid. These and other variations to waterside system 200are within the teachings of the present invention.

Each of subplants 202-212 can include a variety of equipment configuredto facilitate the functions of the subplant. For example, heatersubplant 202 is shown to include a plurality of heating elements 220(e.g., boilers, electric heaters, etc.) configured to add heat to thehot water in hot water loop 214. Heater subplant 202 is also shown toinclude several pumps 222 and 224 configured to circulate the hot waterin hot water loop 214 and to control the flow rate of the hot waterthrough individual heating elements 220. Chiller subplant 206 is shownto include a plurality of chillers 232 configured to remove heat fromthe cold water in cold water loop 216. Chiller subplant 206 is alsoshown to include several pumps 234 and 236 configured to circulate thecold water in cold water loop 216 and to control the flow rate of thecold water through individual chillers 232.

Heat recovery chiller subplant 204 is shown to include a plurality ofheat recovery heat exchangers 226 (e.g., refrigeration circuits)configured to transfer heat from cold water loop 216 to hot water loop214. Heat recovery chiller subplant 204 is also shown to include severalpumps 228 and 230 configured to circulate the hot water and/or coldwater through heat recovery heat exchangers 226 and to control the flowrate of the water through individual heat recovery heat exchangers 226.Cooling tower subplant 208 is shown to include a plurality of coolingtowers 238 configured to remove heat from the condenser water incondenser water loop 218. Cooling tower subplant 208 is also shown toinclude several pumps 240 configured to circulate the condenser water incondenser water loop 218 and to control the flow rate of the condenserwater through individual cooling towers 238.

Hot TES subplant 210 is shown to include a hot TES tank 242 configuredto store the hot water for later use. Hot TES subplant 210 can alsoinclude one or more pumps or valves configured to control the flow rateof the hot water into or out of hot TES tank 242. Cold TES subplant 212is shown to include cold TES tanks 244 configured to store the coldwater for later use. Cold TES subplant 212 can also include one or morepumps or valves configured to control the flow rate of the cold waterinto or out of cold TES tanks 244.

In some embodiments, one or more of the pumps in waterside system 200(e.g., pumps 222, 224, 228, 230, 234, 236, and/or 240) or pipelines inwaterside system 200 include an isolation valve associated therewith.Isolation valves can be integrated with the pumps or positioned upstreamor downstream of the pumps to control the fluid flows in watersidesystem 200. In various embodiments, waterside system 200 can includemore, fewer, or different types of devices and/or subplants based on theparticular configuration of waterside system 200 and the types of loadsserved by waterside system 200.

Referring now to FIG. 3, a block diagram of an airside system 300 isshown, according to an exemplary embodiment. In various embodiments,airside system 300 can supplement or replace airside system 130 in HVACsystem 100 or can be implemented separate from HVAC system 100. Whenimplemented in HVAC system 100, airside system 300 can include a subsetof the HVAC devices in HVAC system 100 (e.g., AHU 106, VAV units 116,ducts 112-114, fans, dampers, etc.) and can be located in or aroundbuilding 10. Airside system 300 can operate to heat or cool an airflowprovided to building 10 using a heated or chilled fluid provided bywaterside system 200.

In FIG. 3, airside system 300 is shown to include an economizer-type airhandling unit (AHU) 302. Economizer-type AHUs vary the amount of outsideair and return air used by the air handling unit for heating or cooling.For example, AHU 302 can receive return air 304 from building zone 306via return air duct 308 and can deliver supply air 310 to building zone306 via supply air duct 312. In some embodiments, AHU 302 is a rooftopunit located on the roof of building 10 (e.g., AHU 106 as shown inFIG. 1) or otherwise positioned to receive Agenth return air 304 andoutside air 314. AHU 302 can be configured to operate exhaust air damper316, mixing damper 318, and outside air damper 320 to control an amountof outside air 314 and return air 304 that combine to form supply air310. Any return air 304 that does not pass through mixing damper 318 canbe exhausted from AHU 302 through exhaust damper 316 as exhaust air 322.

Each of dampers 316-320 can be operated by an actuator. For example,exhaust air damper 316 can be operated by actuator 324, mixing damper318 can be operated by actuator 326, and outside air damper 320 can beoperated by actuator 328. Actuators 324-328 can communicate with an AHUcontroller 330 via a communications link 332. Actuators 324-328 canreceive control signals from AHU controller 330 and can provide feedbacksignals to AHU controller 330. Feedback signals can include, forexample, an indication of a current actuator or damper position, anamount of torque or force exerted by the actuator, diagnosticinformation (e.g., results of diagnostic tests performed by actuators324-328), status information, commissioning information, configurationsettings, calibration data, and/or other types of information or datathat can be collected, stored, or used by actuators 324-328. AHUcontroller 330 can be an economizer controller configured to use one ormore control algorithms (e.g., state-based algorithms, extremum seekingcontrol (ESC) algorithms, proportional-integral (PI) control algorithms,proportional-integral-derivative (PID) control algorithms, modelpredictive control (MPC) algorithms, feedback control algorithms, etc.)to control actuators 324-328.

Still referring to FIG. 3, AHU 302 is shown to include a cooling coil334, a heating coil 336, and a fan 338 positioned within supply air duct312. Fan 338 can be configured to force supply air 310 through coolingcoil 334 and/or heating coil 336 and provide supply air 310 to buildingzone 306. AHU controller 330 can communicate with fan 338 viacommunications link 340 to control a flow rate of supply air 310. Insome embodiments, AHU controller 330 controls an amount of heating orcooling applied to supply air 310 by modulating a speed of fan 338.

Cooling coil 334 can receive a chilled fluid from waterside system 200(e.g., from cold water loop 216) via piping 342 and can return thechilled fluid to waterside system 200 via piping 344. Valve 346 can bepositioned along piping 342 or piping 344 to control a flow rate of thechilled fluid through cooling coil 334. In some embodiments, coolingcoil 334 includes multiple stages of cooling coils that can beindependently activated and deactivated (e.g., by AHU controller 330, byBMS controller 366, etc.) to modulate an amount of cooling applied tosupply air 310.

Heating coil 336 can receive a heated fluid from waterside system 200(e.g., from hot water loop 214) via piping 348 and can return the heatedfluid to waterside system 200 via piping 350. Valve 352 can bepositioned along piping 348 or piping 350 to control a flow rate of theheated fluid through heating coil 336. In some embodiments, heating coil336 includes multiple stages of heating coils that can be independentlyactivated and deactivated (e.g., by AHU controller 330, by BMScontroller 366, etc.) to modulate an amount of heating applied to supplyair 310.

Each of valves 346 and 352 can be controlled by an actuator. Forexample, valve 346 can be controlled by actuator 354 and valve 352 canbe controlled by actuator 356. Actuators 354-356 can communicate withAHU controller 330 via communications links 358-360. Actuators 354-356can receive control signals from AHU controller 330 and can providefeedback signals to controller 330. In some embodiments, AHU controller330 receives a measurement of the supply air temperature from atemperature sensor 362 positioned in supply air duct 312 (e.g.,downstream of cooling coil 334 and/or heating coil 336). AHU controller330 can also receive a measurement of the temperature of building zone306 from a temperature sensor 364 located in building zone 306.

In some embodiments, AHU controller 330 operates valves 346 and 352 viaactuators 354-356 to modulate an amount of heating or cooling providedto supply air 310 (e.g., to achieve a set-point temperature for supplyair 310 or to maintain the temperature of supply air 310 within aset-point temperature range). The positions of valves 346 and 352 affectthe amount of heating or cooling provided to supply air 310 by coolingcoil 334 or heating coil 336 and may correlate with the amount of energyconsumed to achieve a desired supply air temperature. AHU controller 330can control the temperature of supply air 310 and/or building zone 306by activating or deactivating coils 334-336, adjusting a speed of fan338, or a combination of Agenth.

Still referring to FIG. 3, airside system 300 is shown to include abuilding management system (BMS) controller 366 and a client device 368.BMS controller 366 can include one or more computer systems (e.g.,servers, supervisory controllers, subsystem controllers, etc.) thatserve as system level controllers, application or data servers, headnodes, or master controllers for airside system 300, waterside system200, HVAC system 100, and/or other controllable systems that servebuilding 10. BMS controller 366 can communicate with multiple downstreambuilding systems or subsystems (e.g., HVAC system 100, a securitysystem, a lighting system, waterside system 200, etc.) via acommunications link 370 according to like or disparate protocols (e.g.,LON, BACnet, etc.). In various embodiments, AHU controller 330 and BMScontroller 366 can be separate (as shown in FIG. 3) or integrated. In anintegrated implementation, AHU controller 330 can be a software moduleconfigured for execution by a processor of BMS controller 366.

In some embodiments, AHU controller 330 receives information from BMScontroller 366 (e.g., commands, setpoints, operating boundaries, etc.)and provides information to BMS controller 366 (e.g., temperaturemeasurements, valve or actuator positions, operating statuses,diagnostics, etc.). For example, AHU controller 330 can provide BMScontroller 366 with temperature measurements from temperature sensors362-364, equipment on/off states, equipment operating capacities, and/orany other information that can be used by BMS controller 366 to monitoror control a variable state or condition within building zone 306.

Client device 368 can include one or more human-machine interfaces orclient interfaces (e.g., graphical user interfaces, reportinginterfaces, text-based computer interfaces, client-facing web services,web servers that provide pages to web clients, etc.) for controlling,viewing, or otherwise interacting with HVAC system 100, its subsystems,and/or devices. Client device 368 can be a computer workstation, aclient terminal, a remote or local interface, or any other type of userinterface device. Client device 368 can be a stationary terminal or amobile device. For example, client device 368 can be a desktop computer,a computer server with a user interface, a laptop computer, a tablet, asmartphone, a PDA, or any other type of mobile or non-mobile device.Client device 368 can communicate with BMS controller 366 and/or AHUcontroller 330 via communications link 372.

Referring now to FIG. 4, a block diagram of a building management system(BMS) 400 is shown, according to an exemplary embodiment. BMS 400 can beimplemented in building 10 to automatically monitor and control variousbuilding functions. BMS 400 is shown to include BMS controller 366 and aplurality of building subsystems 428. Building subsystems 428 are shownto include a building electrical subsystem 434, an informationcommunication technology (ICT) subsystem 436, a security subsystem 438,a HVAC subsystem 440, a lighting subsystem 442, a lift/escalatorssubsystem 432, and a fire safety subsystem 430. In various embodiments,building subsystems 428 can include fewer, additional, or alternativesubsystems. For example, building subsystems 428 can also oralternatively include a refrigeration subsystem, an advertising orsignage subsystem, a cooking subsystem, a vending subsystem, a printeror copy service subsystem, or any other type of building subsystem thatuses controllable equipment and/or sensors to monitor or controlbuilding 10. In some embodiments, building subsystems 428 includewaterside system 200 and/or airside system 300, as described withreference to FIGS. 2-3.

Each of building subsystems 428 can include any number of devices,controllers, and connections for completing its individual functions andcontrol activities. HVAC subsystem 440 can include many of the samecomponents as HVAC system 100, as described with reference to FIGS. 1-3.For example, HVAC subsystem 440 can include a chiller, a boiler, anynumber of air handling units, economizers, field controllers,supervisory controllers, actuators, temperature sensors, and otherdevices for controlling the temperature, humidity, airflow, or othervariable conditions within building 10. Lighting subsystem 442 caninclude any number of light fixtures, ballasts, lighting sensors,dimmers, or other devices configured to controllably adjust the amountof light provided to a building space. Security subsystem 438 caninclude occupancy sensors, video surveillance cameras, digital videorecorders, video processing servers, intrusion detection devices, accesscontrol devices (e.g., card access, etc.) and servers, or othersecurity-related devices.

Still referring to FIG. 4, BMS controller 366 is shown to include acommunications interface 407 and a BMS interface 409. Interface 407 canfacilitate communications between BMS controller 366 and externalapplications (e.g., monitoring and reporting applications 422,enterprise control applications 426, remote systems and applications444, applications residing on client devices 448, etc.) for allowinguser control, monitoring, and adjustment to BMS controller 366 and/orsubsystems 428. Interface 407 can also facilitate communications betweenBMS controller 366 and client devices 448. BMS interface 409 canfacilitate communications between BMS controller 366 and buildingsubsystems 428 (e.g., HVAC, lighting security, lifts, powerdistribution, business, etc.).

Interfaces 407, 409 can be or include wired or wireless communicationsinterfaces (e.g., jacks, antennas, transmitters, receivers,transceivers, wire terminals, etc.) for conducting data communicationswith building subsystems 428 or other external systems or devices. Invarious embodiments, communications via interfaces 407, 409 can bedirect (e.g., local wired or wireless communications) or via acommunications network 446 (e.g., a WAN, the Internet, a cellularnetwork, etc.). For example, interfaces 407, 409 can include an Ethernetcard and port for sending and receiving data via an Ethernet-basedcommunications link or network. In another example, interfaces 407, 409can include a Wi-Fi transceiver for communicating via a wirelesscommunications network. In another example, one or Agenth of interfaces407, 409 can include cellular or mobile phone communicationstransceivers. In one embodiment, communications interface 407 is a powerline communications interface and BMS interface 409 is an Ethernetinterface. In other embodiments, Agenth communications interface 407 andBMS interface 409 are Ethernet interfaces or are the same Ethernetinterface.

Still referring to FIG. 4, BMS controller 366 is shown to include aprocessing circuit 404 including a processor 406 and memory 408.Processing circuit 404 can be communicably connected to BMS interface409 and/or communications interface 407 such that processing circuit 404and the various components thereof can send and receive data viainterfaces 407, 409. Processor 406 can be implemented as a generalpurpose processor, an application specific integrated circuit (ASIC),one or more field programmable gate arrays (FPGAs), a group ofprocessing components, or other suitable electronic processingcomponents.

Memory 408 (e.g., memory, memory unit, storage device, etc.) can includeone or more devices (e.g., RAM, ROM, Flash memory, hard disk storage,etc.) for storing data and/or computer code for completing orfacilitating the various processes, layers and modules described in thepresent application. Memory 408 can be or include volatile memory ornon-volatile memory. Memory 408 can include database components, objectcode components, script components, or any other type of informationstructure for supporting the various activities and informationstructures described in the present application. According to anexemplary embodiment, memory 408 is communicably connected to processor406 via processing circuit 404 and includes computer code for executing(e.g., by processing circuit 404 and/or processor 406) one or moreprocesses described herein.

In some embodiments, BMS controller 366 is implemented within a singlecomputer (e.g., one server, one housing, etc.). In various otherembodiments BMS controller 366 can be distributed across multipleservers or computers (e.g., that can exist in distributed locations).Further, while FIG. 4 shows applications 422 and 426 as existing outsideof BMS controller 366, in some embodiments, applications 422 and 426 canbe hosted within BMS controller 366 (e.g., within memory 408).

Still referring to FIG. 4, memory 408 is shown to include an enterpriseintegration layer 410, an automated measurement and validation (AM&V)layer 412, a demand response (DR) layer 414, a fault detection anddiagnostics (FDD) layer 416, an integrated control layer 418, and abuilding subsystem integration later 420. Layers 410-420 can beconfigured to receive inputs from building subsystems 428 and other datasources, determine optimal control actions for building subsystems 428based on the inputs, generate control signals based on the optimalcontrol actions, and provide the generated control signals to buildingsubsystems 428. The following paragraphs describe some of the generalfunctions performed by each of layers 410-420 in BMS 400.

Enterprise integration layer 410 can be configured to serve clients orlocal applications with information and services to support a variety ofenterprise-level applications. For example, enterprise controlapplications 426 can be configured to provide subsystem-spanning controlto a graphical user interface (GUI) or to any number of enterprise-levelbusiness applications (e.g., accounting systems, user identificationsystems, etc.). Enterprise control applications 426 can also oralternatively be configured to provide configuration GUIs forconfiguring BMS controller 366. In yet other embodiments, enterprisecontrol applications 426 can work with layers 410-420 to optimizebuilding performance (e.g., efficiency, energy use, comfort, or safety)based on inputs received at interface 407 and/or BMS interface 409.

Building subsystem integration layer 420 can be configured to managecommunications between BMS controller 366 and building subsystems 428.For example, building subsystem integration layer 420 can receive sensordata and input signals from building subsystems 428 and provide outputdata and control signals to building subsystems 428. Building subsystemintegration layer 420 can also be configured to manage communicationsbetween building subsystems 428. Building subsystem integration layer420 translate communications (e.g., sensor data, input signals, outputsignals, etc.) across a plurality of multi-vendor/multi-protocolsystems.

Demand response layer 414 can be configured to optimize resource usage(e.g., electricity use, natural gas use, water use, etc.) and/or themonetary cost of such resource usage in response to satisfy the demandof building 10. The optimization can be based on time-of-use prices,curtailment signals, energy availability, or other data received fromutility providers, distributed energy generation systems 424, fromenergy storage 427 (e.g., hot TES 242, cold TES 244, etc.), or fromother sources. Demand response layer 414 can receive inputs from otherlayers of BMS controller 366 (e.g., building subsystem integration layer420, integrated control layer 418, etc.). The inputs received from otherlayers can include environmental or sensor inputs such as temperature,carbon dioxide levels, relative humidity levels, air quality sensoroutputs, occupancy sensor outputs, room schedules, and the like. Theinputs can also include inputs such as electrical use (e.g., expressedin kWh), thermal load measurements, pricing information, projectedpricing, smoothed pricing, curtailment signals from utilities, and thelike.

According to an exemplary embodiment, demand response layer 414 includescontrol logic for responding to the data and signals it receives. Theseresponses can include communicating with the control algorithms inintegrated control layer 418, changing control strategies, changingsetpoints, or activating/deactivating building equipment or subsystemsin a controlled manner. Demand response layer 414 can also includecontrol logic configured to determine when to utilize stored energy. Forexample, demand response layer 414 can determine to begin using energyfrom energy storage 427 just prior to the beginning of a peak use hour.

In some embodiments, demand response layer 414 includes a control moduleconfigured to actively initiate control actions (e.g., automaticallychanging setpoints) which minimize energy costs based on one or moreinputs representative of or based on demand (e.g., price, a curtailmentsignal, a demand level, etc.). In some embodiments, demand responselayer 414 uses equipment models to determine an optimal set of controlactions. The equipment models can include, for example, thermodynamicmodels describing the inputs, outputs, and/or functions performed byvarious sets of building equipment. Equipment models can representcollections of building equipment (e.g., subplants, chiller arrays,etc.) or individual devices (e.g., individual chillers, heaters, pumps,etc.).

Demand response layer 414 can further include or draw upon one or moredemand response policy definitions (e.g., databases, XML, files, etc.).The policy definitions can be edited or adjusted by a user (e.g., via agraphical user interface) so that the control actions initiated inresponse to demand inputs can be tailored for the user's application,desired comfort level, particular building equipment, or based on otherconcerns. For example, the demand response policy definitions canspecify which equipment can be turned on or off in response toparticular demand inputs, how long a system or piece of equipment shouldbe turned off, what setpoints can be changed, what the allowable setpoint adjustment range is, how long to hold a high demand set-pointbefore returning to a normally scheduled set-point, how close toapproach capacity limits, which equipment modes to utilize, the energytransfer rates (e.g., the maximum rate, an alarm rate, other rateboundary information, etc.) into and out of energy storage devices(e.g., thermal storage tanks, battery banks, etc.), and when to dispatchon-site generation of energy (e.g., via fuel cells, a motor generatorset, etc.).

Integrated control layer 418 can be configured to use the data input oroutput of building subsystem integration layer 420 and/or demandresponse later 414 to make control decisions. Due to the subsystemintegration provided by building subsystem integration layer 420,integrated control layer 418 can integrate control activities of thesubsystems 428 such that the subsystems 428 behave as a singleintegrated supersystem. In an exemplary embodiment, integrated controllayer 418 includes control logic that uses inputs and outputs from aplurality of building subsystems to provide greater comfort and energysavings relative to the comfort and energy savings that separatesubsystems could provide alone. For example, integrated control layer418 can be configured to use an input from a first subsystem to make anenergy-saving control decision for a second subsystem. Results of thesedecisions can be communicated back to building subsystem integrationlayer 420.

Integrated control layer 418 is shown to be logically below demandresponse layer 414. Integrated control layer 418 can be configured toenhance the effectiveness of demand response layer 414 by enablingbuilding subsystems 428 and their respective control loops to becontrolled in coordination with demand response layer 414. Thisconfiguration may advantageously reduce disruptive demand responsebehavior relative to conventional systems. For example, integratedcontrol layer 418 can be configured to assure that a demandresponse-driven upward adjustment to the set-point for chilled watertemperature (or another component that directly or indirectly affectstemperature) does not result in an increase in fan energy (or otherenergy used to cool a space) that would result in greater total buildingenergy use than was saved at the chiller.

Integrated control layer 418 can be configured to provide feedback todemand response layer 414 so that demand response layer 414 checks thatconstraints (e.g., temperature, lighting levels, etc.) are properlymaintained even while demanded load shedding is in progress. Theconstraints can also include set-point or sensed boundaries relating tosafety, equipment operating limits and performance, comfort, fire codes,electrical codes, energy codes, and the like. Integrated control layer418 is also logically below fault detection and diagnostics layer 416and automated measurement and validation layer 412. Integrated controllayer 418 can be configured to provide calculated inputs (e.g.,aggregations) to these higher levels based on outputs from more than onebuilding subsystem.

Automated measurement and validation (AM&V) layer 412 can be configuredto verify that control strategies commanded by integrated control layer418 or demand response layer 414 are working properly (e.g., using dataaggregated by AM&V layer 412, integrated control layer 418, buildingsubsystem integration layer 420, FDD layer 416, or otherwise). Thecalculations made by AM&V layer 412 can be based on building systemenergy models and/or equipment models for individual BMS devices orsubsystems. For example, AM&V layer 412 can compare a model-predictedoutput with an actual output from building subsystems 428 to determinean accuracy of the model.

Fault detection and diagnostics (FDD) layer 416 can be configured toprovide on-going fault detection for building subsystems 428, buildingsubsystem devices (i.e., building equipment), and control algorithmsused by demand response layer 414 and integrated control layer 418. FDDlayer 416 can receive data inputs from integrated control layer 418,directly from one or more building subsystems or devices, or fromanother data source. FDD layer 416 can automatically diagnose andrespond to detected faults. The responses to detected or diagnosedfaults can include providing an alert message to a user, a maintenancescheduling system, or a control algorithm configured to attempt torepair the fault or to work-around the fault.

FDD layer 416 can be configured to output a specific identification ofthe faulty component or cause of the fault (e.g., loose damper linkage)using detailed subsystem inputs available at building subsystemintegration layer 420. In other exemplary embodiments, FDD layer 416 isconfigured to provide “fault” events to integrated control layer 418which executes control strategies and policies in response to thereceived fault events. According to an exemplary embodiment, FDD layer416 (or a policy executed by an integrated control engine or businessrules engine) can shut-down systems or direct control activities aroundfaulty devices or systems to reduce energy waste, extend equipment life,or assure proper control response.

FDD layer 416 can be configured to store or access a variety ofdifferent system data stores (or data points for live data). FDD layer416 can use some content of the data stores to identify faults at theequipment level (e.g., specific chiller, specific AHU, specific terminalunit, etc.) and other content to identify faults at component orsubsystem levels. For example, building subsystems 428 can generatetemporal (i.e., time-series) data indicating the performance of BMS 400and the various components thereof. The data generated by buildingsubsystems 428 can include measured or calculated values that exhibitstatistical characteristics and provide information about how thecorresponding system or process (e.g., a temperature control process, aflow control process, etc.) is performing in terms of error from itsset-point. These processes can be examined by FDD layer 416 to exposewhen the system begins to degrade in performance and alert a user torepair the fault before it becomes more severe.

BMS Performance Assessment Tool

The BMS, as described above, has multiple individual components withinthe BMS. Example components may include control devices, such as fieldequipment controllers (FECs), advanced application field equipmentcontrollers (FAC), network control engines (NCEs), input/output modules(IOMs), and variable air volume (VAV) modular assemblies. However, othercontrol device types are contemplated. Further, the BMS may includeequipment such as actuators, valves, AHUs, RTUs, thermostats, or anyother device associated with the BMS, which are controlled by thecontrol devices described above. In some examples, these devices may bemonitored using a centralized monitoring tool, such as a controllerconfiguration tool (CCT) from Johnson Controls. However, othermonitoring tools are contemplated.

Referring now to FIG. 5, a block diagram showing a performanceassessment tool 500 is provided, according to some embodiments. Theperformance assessment tool 500 is shown to include a processing circuit502. The processing circuit 502 includes a processor 504 and a memory506. The processor 504 may be a general purpose or specific purposeprocessor, an application specific integrated circuit (ASIC), one ormore field programmable gate arrays (FPGAs), a group of processingcomponents, or other suitable processing components. The processor 504may be configured to execute computer code or instructions stored in thememory 506 or received from other computer readable media (e.g., CDROM,network storage, a remote server, etc.).

The memory 506 may include one or more devices (e.g., memory units,memory devices, storage devices, etc.) for storing data and/or computercode for completing and/or facilitating the various processes describedin the present disclosure. The memory 506 may include random accessmemory (RAM), read-only memory (ROM), hard drive storage, temporarystorage, non-volatile memory, flash memory, optical memory, or any othersuitable memory for storing software objects and/or computerinstructions. The memory 506 may include database components, objectcode components, script components, or any other type of informationstructure for supporting the various activities and informationstructures described in the present disclosure. The memory 506 may becommunicably connected to the processor 504 via processing circuit 502and may include computer code for executing (e.g., by processor 504) oneor more processes described herein.

The memory 506 may include a performance evaluation module 508. Theperformance evaluation module 508 may include a number of additionalmodules, such as a system inventory module 510, a system performancemodule 512, and a system feature module 514. The performance assessmenttool 500 may further include a BMS communication interface 518, a userinterface 520, and a communication interface 522 for communicating witha network 524.

In one embodiment, the performance assessment tool 500 receives datafrom a BMS 526 via the BMS communication interface 518. In one example,the BMS communication interface 518 may access the BMS via a BMS accessdevice 528. The BMS interface device 528 may be any type of BMSinterface device. In one embodiment, the BMS interface device 528 is amobile access point (MAP) device, such as a MAP Gateway device byJohnson Controls. In other embodiments, the BMS interface device 528 maybe a Metasys server from Johnson Controls. The BMS access device 528 maybe configured to collect data from the BMS 526, and may provide thisdata to the performance assessment tool 500 upon request. In oneembodiment, the BMS access device 528 may be configured to receive arequest for data from the performance assessment tool 500 and access theBMS 526 to collect the requested data. The requested data may be pointdata, object data, etc. However, other devices with access to a BMSnetwork 530 within the BMS 526 are also contemplated, such as smartthermostats, dedicated BMS controllers, home hubs, or other connecteddevices. The BMS communication interface 518 may provide a communicationlink to the BMS 526. In one embodiment, the communication interface 518is a serial interface, such as RS-232 or RS-485. In some examples, theBMS communication interface 518 may be a wireless interface such as acellular (3G, 4G, CDMA, LTE, etc.) interface, a Wi-Fi interface, aZigbee interface, a Bluetooth interface, a LoRa interface, etc. In otherexample, the BMS communication interface 518 may be other wiredinterfaces such as USB, Firewire, Lightning Connections, CAT5 (wiredEthernet), etc.

The BMS 526 may include a BMS network 530, one or more BMS controllers532, and a number of BMS devices, such as BMS devices 534, 536. The BMScontroller 532, and the BMS devices 534, 536 may be any of thecontroller or devices as described above in regards to FIGS. 1-4, above.In one example, the BMS network 530 may provide communication betweenthe BMS controller 532, the BMS devices 534, 536 and the BMS accessdevice 528. In one embodiment, the BMS network 530 is a BACnet network.In other embodiments, the BMS network 530 is an EthernetIP network.Alternatively, the BMS network 530 may be any other type of BMS network,as applicable.

In one embodiment, the performance assessment tool 500 is a web-basedtool. For example, the performance assessment tool 500 may be hosted ona server, and accessed via a connection to the network 524 via thecommunication interface 522. In some examples, network 524 may be alocal network such as a local area network (LAN), or a wide area network(WAN). In other examples, the network 524 may be an internet basednetwork, which may allow a user to access the performance assessmenttool 500 using a web browser, such as an HTML web browser. In otherembodiments, the performance assessment tool 500 may be hosted on aserver and accessed using a thin-client. In some embodiments, a user maybe able to access the performance assessment tool 500 using a mobiledevice 538 having a connection to the network 524. For example, mobiledevices such as smartphones (iPhone, Android phone, Windows phone,etc.), tablet computers (iPad, Android tablet, Windows Surface, etc.),mobile computers (laptops, netbooks), stationary computers (PCs), ordedicated devices having a network interface which may be used to accessthe network 524. Dedicated devices may include smart thermostats,dedicated BMS controllers, home hubs, or access point devices such as amobile access point (MAP) device from Johnson Controls. In otherembodiments, the performance assessment tool 500 may be loaded onto athick-client device, such as a laptop, personal computer (PC), or othercomputing device which can communicate with the BMS 526. In someexamples, where the performance assessment tool 500 is loaded onto athick-client device, a user may access the tool via the user interface520. For example, the user interface 520 may be a user interface of thethick-client device.

In one embodiment, the system inventory module 510 may be configured toaccess the BMS 526 via the BMS communication interface 518 and generatean inventory list of all devices associated with the BMS 526. Thisinventory may include all devices, controllers, communication devices,access points, or any other portion of the BMS 526. The generation ofinventory lists using the system inventory module 510 will be describedin more detail below. In one embodiment, the system performance module512 is configured to access the BMS 526 via the BMS communicationinterface 518 and to retrieve information related to the performance ofthe BMS 526. The system performance module 512 may further analyze thedata retrieved from the BMS 526 to generate one or more BMS performancereports, as described in further detail below. In a further embodiment,the system features module 514 is configured to access the BMS 526 viathe BMS communication interface 518 and to retrieve information relatedto features associated with the BMS 526.

In one embodiment, the performance assessment tool 500 may be incommunication with a knowledgebase 540. The knowledgebase 540 may beaccessed by the performance assessment tool 500 via the network 524. Theknowledgebase 540 may include information required by the performanceassessment tool 500 to accurately perform the performance verificationprocesses, as described below. In one embodiment, the knowledgebase 540may include existing specifications for a number of BMS systems. Theknowledgebase 540 may further include facility data from locations wherethe BMS systems are installed. Facility data may include physical plantschematics, riser diagrams, installed components, maintenance records,service contracts, etc. The knowledgebase 540 may further includehistorical data such as prior performance assessments, inventoryassessments or feature assessments, as described in detail below. In oneembodiment, the knowledgebase 540 may be a central repository for alldata collected via one or more performance assessment tools.

Turning now to FIG. 6, a flow chart illustrating a licensing process 600for a performance assessment tool 500 is shown, according to someembodiments. In one embodiment, the performance assessment tool 500 isthe performance assessment tool 500 described above. At process block602, a user may enter a license for the performance assessment tool 500.In some embodiments, the user may be prompted by the performanceassessment tool 500 to provide the license when the performanceassessment tool 500 is first launched. In other embodiments, the usermay be prompted to enter a license whenever the performance assessmenttool 500 is used in a new BMS. In still further embodiments, the usermay be prompted to enter a license every time the performance assessmenttool 500 is activated. Once the license is entered at process block 602,the license is validated at process block 604. In one example, the usermay be instructed to contact an administrator if the entered license isunable to be validated.

Turning now to FIG. 7, a flow chart illustrating a system inventoryingprocess 700 is shown, according to some embodiments. As shown in FIG. 7,a user 702, may select an option to initiate the system inventoryingprocess 700 by creating a new inventory project at process block 704.Turning briefly to FIG. 8, a screen shot of the performance assessmenttool 500 is shown illustrating a dialog box 800 for generating a newinventory project. The dialog box 800 may have a project name input 802,a branch input 804, and a field technician name input 806. The projectname input 802 may be used to provide a unique identifier for theproject. The branch input 804 may be used to provide an indication as towhat BMS, and/or what portion of a BMS is being evaluated. Additionally,the field technician name input 806 may be used to enter the name of thefield technician generating the project.

Returning now to FIG. 7, once the user 702 has created the new inventoryproject, the performance assessment tool 500 may scan the live BMSsystem at process block 706. In one embodiment, the performanceassessment tool 500 may query the BMS system to request informationrelated to every device or component within the BMS. In otherembodiments, the performance assessment tool 500 may query the BMSsystem to request information related to a portion of the BMS system tobe evaluated. The performance assessment tool 500 may further scan anarchive associated with the BMS system being scanned at process block708. In one embodiment, the archive is stored in the knowledgebase 540.However, in other examples, the archive may be stored in the memory 506of the performance assessment tool 500. By scanning the archive, theperformance assessment tool 500 may be able to determine if previousinventory projects had been created for the given BMS system. At processblock 710, the results of the inventory project may be presented to theuser 702. In one embodiment, the results may be presented in a listform. In other embodiments, the results may be displayed to a uservisually, such as via a connection diagram. Once the results arepresented to the user 702, the user 702 may instruct the performanceassessment tool 500 to perform multiple operations. In one embodiment,the user may instruct the performance assessment tool 500 to save theproject at process block 712. In a further embodiment, the user 702 mayinstruct the performance assessment tool 500 to export the results atprocess block 714. For example, where the results are in list form, theresults may be exported to a spreadsheet, such as a Microsoft Excelspreadsheet. In other examples, the results may be exported to agraphics program, such as Microsoft Visio, where the results are in avisual form. Further, additional programs are contemplated, as well asexporting to multiple programs at once.

In a further embodiment, the user 702 may instruct the performanceassessment tool 500 to analyze the results at process block 716. In oneembodiment, the system inventory module 510 of the performanceassessment tool 500 may be used to analyze the results provided inprocess block 710. The analysis may include determining firmwareversions are installed on the devices of the BMS, and determining ifthey are out of date, evaluating when the last maintenance was performedon the devices within the BMS, determining when the last database backupof a BMS occurred, evaluating if any devices within the BMS are outdatedor obsolete, and/or other analysis requested by the user 702. Once theanalysis is completed, the user 702 may instruct the performanceassessment tool 500 to generate a report at process block 718. In oneembodiment, the report may include information determined during theanalysis at process block 716. In a further embodiment, the user 702 mayinstruct the performance assessment tool 500 to generate a report atprocess block 718 based on the result provided at process block 710.

Turning now to FIG. 10, a screen shot of the performance assessment tool500 is shown illustrating an example report 1000. In one embodiment, thereport 1000 may include one or more statuses of the BMS being analyzed.For example, the report may include a site information portion 1002. Thesite information portion 1002 may provide general status informationabout the BMS being analyzed, such as number of servers, supervisorydevices, controllers, and data points in the scanned BMS. The siteinformation portion 1002 may further include information related to thefirmware of the various devices in the BMS. For example, the siteinformation portion 1002 indicates the firmware versions associated witha number of network automation engine (NAE) controllers in the BMS. Thereport 1000 may further include a critical issues portion 1004, acorrective maintenance portion 1006, and a key tasks portion 1008. Thecritical issues portion may provide a list of all the issues determinedto be critical during the analysis. The corrective maintenance portion1006 may provide general information related to corrective maintenancerequired to fix issues identified during the analysis. Finally, the keytasks portion 1008 may provide information to a user regarding actionsthat need to be taken to address the identified critical issues.Finally, the report 1000 may include a server information portion 1010,which may provide information relating to a server within the BMS. Whilethe above report is shown with the above described portions, it iscontemplated that the reports may be user configurable to include moreinformation or less information, as desired by the user.

Once the report has been generated at process block 718, the user 702may instruct the performance assessment tool 500 to generate a proposalat process block 720. The proposal may format the information providedin the report generated at process block 718 to be provided to acustomer. The proposal may include additional information from thereport, such as potential costs, potential savings, timelines, etc. Inan alternate embodiment, the user may instruct the performanceassessment tool 500 to generate the proposal at process block 720 uponexporting the results at process block 714. The generated proposal mayinclude information related to the unanalyzed results provided atprocess block 710 in a format suitable for presentation to a customer orother end user.

The user 702 may further instruct the performance assessment tool 500 toopen an existing inventory project at process block 722. The user mayselect a previously created inventory project stored in the memory 506of the performance assessment tool 500. For example, the user 702 mayselect a previously created inventory project stored in the memory 506to update a previously performed inventory project with updated systeminformation. Once the user 702 opens the existing inventory project, theprocess 700 may follow the steps described above for when the user 702creates a new inventory project. Specifically, the process can scan thelive BMS system at process block 706, as well as scan an archive atprocess block 708. The results can be presented at process block 710,and a user may then instruct the performance assessment tool 500 to savethe project at process block 712, export the results at process block714, analyze the results at process block 716 and/or generate a reportat process block 718. Further, the user may instruct the performanceassessment tool 500 to generate a proposal based on either the analyzedresults or the unanalyzed results as described above. In one embodiment,the performance assessment tool 500 may save the project outputs (e.g.results, reports and/or proposals) in a new file, to allow for futurecomparison.

In a further embodiment, the user 702 may instruct the performanceassessment tool 500 to perform a comparison assessment at process block724. The comparison assessment may provide a comparison in time betweentwo or more previously generated inventory projects. In one embodiment,the comparison assessment may compare the results between two or moresets of previously generated results sets for a given BMS. At processblock 724, the user 702 can select two or more files to compare. Turningbriefly now to FIG. 9, a dialog box illustrating a file comparisoninterface 900 is shown, according to some embodiments. As shown in FIG.9, the user may select a first project file using the first project fileinput 902, and a second project file using the second project file input904. The first project file may be a current assessment of the BMS, or apreviously generated assessment of the BMS. The user may then selectwhat type of comparison is desired (i.e. inventory) using the comparetype input 906. Returning now to FIG. 7, once the user 702 selects thefiles to be compared at process block 724, user 702 can instruct theperformance assessment tool 500 to perform an analysis at process block716. The analysis may determine all differences in the inventory of theBMS between the two selected files. Once the analysis is completed, theuser may instruct the performance assessment tool 500 to generate areport at process block 718. In some embodiments, the user 702 mayinstruct the performance assessment tool 500 to generate the report atprocess block 718 once the two files are selected for comparison. Thismay generate a report including a basic comparison between the twofiles.

In one embodiment, the user 702 may instruct the performance assessmenttool 500 to generate a system comparison report at process block 718. Anexample system comparison report 1100 is shown in FIG. 11. The report1100 may include a first inventory report portion 1102 and secondinventory report portion 1104. The first inventory report portion 1102and the second inventory report portion may allow the user 702 tocompare the critical issues, preventative maintenance, key tasks, serverinformation and site information between the two inventory reports. Inone embodiment, the comparison report compares two inventory reports attwo different points in time. For example, the first inventory reportportion 1102 may be a current inventory of the system, and the secondinventory report portion may reflect an inventory of the system from oneyear prior. In some embodiments, the user 702 can specify the period oftime for the comparison. It is contemplated that more information orless information may be provided in the report 1100. For example, theuser 702 may be able to specify what information is required to be shownin the report.

Turning now to FIG. 12, a comparison summary report 1200 is shown,according to some embodiments. The comparison summary report 1200 mayinclude a site information portion 1202. The site information portion1202 may show only the differences from an earlier inventory project. Asshown in the site information portion 1202, it is shown that thesupervisory devices have increased by seven, the number of controllershas increased by one hundred and twenty-five, and the total point counthas increased by six hundred and forty-two. This can provide the user702 with a quick understanding on the changes in the BMS system sincethe last inventory project was run, or the changes between the BMSsystem inventory at two points in time. Further, a critical issuesportion 1204, a preventative maintenance portion 1206, and a key tasksportion 1208 may further show the differences between the criticalissues, the preventative maintenance requirements, and the keys tasksbetween BMS inventory reports generated at two different points in time.For example, the critical issues portion 1204 may describe the changesin any critical issues between the inventory projects, such as a “2%increase in supervisory devices exceeding MSEA limitations.” Similar tothe comparison report 1100, the comparison summary report 1200 may showthe changes in a system inventory over a period of time. For example,the comparison summary report may show the changes in the inventory ofthe system over the course of one year. However, in other embodiments,the user 702 can specify the period of time over which the comparison isperformed.

Returning now to FIG. 7, once the report has been generated at processblock 718, the user may instruct the performance assessment tool 500 togenerate a proposal at process block 720. The proposal may include theinformation contained in the generated reports presented in a formatappropriate for presenting to a customer or end user. The inventoryingprocess 700 may be used to verify that the BMS systems has been properlyinstalled or commissioned. In some embodiments, the inventorying process700 is used to verify that any additions to the BMS are properlyinstalled. In further embodiments, the inventorying process 700 is usedto provide user with multiple reports showing the changes to a systemover time. These changes may be used to determine what optimizations,improvements, or additional maintenance is needed in the system.

Turning now to FIG. 13A, a flow chart illustrating a system performanceassessment process 1300 is shown, according to some embodiments. A user1302 may initiate the process by opening an existing project at processblock 1304. The project may be an inventory project as described above.The process may then provide an existing hardware list to the user 1302at process block 1306. The user 1302 may then select specific hardwarewithin the BMS system from the list of existing hardware at processblock 1308. In one embodiment, the user 1302 may select all the hardwarerelated to a specific area of the BMS system. For example, the user 1302may select all of the hardware associated with a specific building orarea controlled by the BMS. In other examples, the user 1302 may selectall of the hardware associated with a particular system or sub-systemwithin the BMS.

Once the user 1302 has selected the specific hardware to be analyzed atprocess block 1308, the process 1300 may scan the live system at processblock 1310. In one embodiment, the system is scanned using a performanceassessment tool, such as performance assessment tool 500 describedabove. In other embodiments, the performance assessment tool 500instructs another device, such as the BMS access device 528 describedabove, to scan the system. For example, the performance assessment tool500 may communicate with a Metasys server to perform the specificactions required to collect the data from the BMS based on the scans theuser selected. The system may then be scanned to retrieve one or moreattributes and/or parameters associated with the hardware componentsselected at process block 1308. Example attributes may include firmwarestatus, backup status, model number, associated devices, etc. Exampleparameters may include filter status, motor current values, optimizationparameters active, air pressure values, etc. Once the system has beenscanned at process block 1310, an updated hardware list and associatedperformance information may be determined based on the receivedattributes and/or parameters for multiple aspects of the BMS, at processblock 1312. The performance information may include general performancedata, such as equipment operating schedules, motor status, set points,general operation, etc. Further, other performance information mayinclude maintenance and reliability data such as filter statuses,equipment operating hours, alarms, improper device addressing, missingtrends, backup status, and the like. Further performance information mayinclude security and standards data, such as number of administrativeusers, number of default passwords in use, U/L listed devices, knownfirmware vulnerabilities, number of dormant accounts, pointcategorization, and the like. Still further performance information mayinclude comfort and health data, such as temperature variations fromsetpoints, pressure variations from setpoints, CO2 variations fromsetpoint, and the like.

In one embodiment, the updated hardware list and/or the associatedperformance information is provided to the user via the user interface520 of the performance assessment tool 500. In other embodiments, theupdated hardware list and/or the associated performance information isprovided to the user on a mobile device, such as mobile device 538. Forexample, the performance assessment tool 500 may transmit the updatedhardware list and/or the associated performance information to themobile device 538 via the network 524. In some embodiments, the updatedhardware list and/or the associated performance information is providedto the user in a table format. For example, the data may be provided tothe user in a spreadsheet format, such as a Microsoft Excel table.

The process 1300 may then perform an analysis of the system based on theupdated hardware list and associated performance info provide to theuser 1302 at process block 1314. In one embodiment, the analysis isperformed by the system performance module 512 of the performanceassessment tool 500. The analysis may include analyzing the performancedata to determine one or more performance metrics associated with theBMS. The performance metrics may be provided for various aspects of theBMS, such as performance and savings, maintenance and reliability,security and standards, comfort and health, or the like. In someexamples, the performance metrics may be provided for various systems orsubsystems within the BMS. For example, the performance metrics may beassociated with an entire campus, one or more building located on thecampus, and/or one or more areas within the building. Similarly theperformance metrics may be associated with systems such as lighting,HVAC, etc. Examples of other portions of the BMS associated with theperformance metrics are further described in the performance assessmentsummary report described below.

In one embodiment, the metrics include numerical scores associated withthe performance one or more aspects of the BMS. The numerical scores mayrepresent a general level of performance of the BMS. In some examples,the numerical scores can be determined based on benchmarked scores fromother BMS systems. For example, the knowledgebase 540 may includeperformance data for multiple BMS systems. The performance metrics maytherefore determine the numerical scores associated with the performanceof the aspects of the BMS based on comparing the performance of the BMS526 to the performance of one or more similar BMS systems. In otherembodiments, the numerical scores may be determined based onpredetermined scoring criteria. In some examples, the predeterminedscoring criteria may be set by a user associated with the BMS 526. Inother examples, the predetermined scoring criteria may be a definedalgorithm programmed into the performance assessment tool 500. In oneembodiment, the predetermined scoring criteria is based on previousanalysis of various BMS systems. The predetermined scoring criteria maybe stored in the memory 506 of the performance assessment tool 500.

Additionally, the performance assessment tool 500 may analyze theperformance data and the associated hardware devices to generateimprovement opportunities related to the BMS. Example improvementopportunities may include backing up the system database, upgradingfirmware associated with various controllers, replacing filters,properly addressing devices, correctly binding references within theBMS, etc. The improvement opportunities may further include:modifications to equipment operation schedules, utilization ofeconomizer strategies, reducing a number of administrative users, propersizing of motors, modification or AHU reset strategies, and/oradditional feature utilization. The above list is exemplary only, and itis considered that additional improvement opportunities may be providedbased on the individual BMS being analyzed.

In one embodiment, the performance assessment tool 500 may communicatewith a knowledgebase, such as knowledgebase 540, to access informationrelating to the analysis of the system. The knowledgebase 540 mayinclude data relating to performing an analysis in general. In otherembodiments, the knowledgebase 540 may contain historical data fromprevious analysis performed, which may be used by the performanceassessment tool 500 to conduct the analysis at process block 1314. Infurther embodiments, the knowledgebase 540 may further containperformance data associated with one or more other BMS systems. Further,the performance assessment tool 500 may provide the results of theanalysis, as well as the gathered data from process block 1314, to theknowledgebase 540.

At process block 1316, the analysis results are provided to the user1302. In one embodiment, the analysis results include the improvementopportunities determined during the analysis, along with the hardwarelist and performance information presented at process block 1312.Turning now to FIG. 14, a screen shot of the performance assessment tool500 illustrating a performance assessment summary 1400 is shown,according to some embodiments. The performance assessment summary 1400may include a site information portion 1402. The site informationportion 1402 may include a summary overview of the system, or portion ofthe system being analyzed. The performance assessment summary 1400 mayfurther include a performance and savings summary 1404, a maintenanceand reliability summary 1406, a security and standards summary 1408, anda comfort and health summary 1410.

The performance and savings summary 1404 may include data related tovarious system performance items, as well as potential savings that maybe available. For example, the performance and savings summary 1404 mayinclude data related to scheduling, economizers, fan motors, AHU supplyfan static pressure resets, AHU discharge air temp resets, 100% outdoorAHU, and number of heating valves open compared to other systems. Theperformance and savings summary 1404 may further include a performanceand savings system score 1412. The performance and savings system score1412 may provide a numerical score indicating the determined performanceand savings associated with the system. In one embodiment, the numericalscore may be between one and ten, with ten representing the best scorefor a system. However, other scoring schema are also considered. Forexample, the performance and savings score 1412 may be an alphabeticalrating system (e.g. A, B, C, D, F). In further embodiments, theperformance and savings system score 1412 may be highlighted to providea visual indication of the overall score. For example, red may indicatea poor performance score, yellow a neutral performance score, and greena high performance score.

The maintenance and reliability summary 1406 may include data related tothe maintenance and reliability of various devices within the system.For example, the maintenance and reliability summary 1406 may providedata related to required or suggested maintenance, data available, etc.Example data may include dirty filter data, chiller operating hoursdata, unbound references data, improperly addressed devices data,missing trends data, alarms/events data, % site exceeding MSEArecommendations data, and/or last backup of the system. The maintenanceand reliability summary may further include a maintenance andreliability score 1414. The maintenance and reliability score 1414 mayprovide a numerical score indicating the determined performance andsavings associated with the system. In one embodiment, the numericalscore may be between one and ten, with ten representing the best scorefor a system. However, other scoring schema are also considered. Forexample, the maintenance and reliability score 1414 may be analphabetical rating system (e.g. A, B, C, D, F). In further embodiments,the maintenance and reliability score 1414 may be highlighted to providea visual indication of the overall score. For example, red may indicatea poor performance score, yellow a neutral performance score, and greena high performance score.

The security and standards summary 1408 may include data related tosecurity and standards items associated with the system. For example,the security and standards summary 1408 may include data related todefault password usage, number of administrative users, U/L listeddevices, firmware vulnerabilities, number of dormant accounts, pointcategorization, and standard naming conventions. However, additionaldata points are contemplated. The security and standards summary 1408may further include a security and standards score 1416. The securityand standards score 1416 may provide a numerical score indicating thedetermined performance and savings associated with the system. In oneembodiment, the numerical score may be between one and ten, with tenrepresenting the best score for a system. However, other scoring schemaare also considered. For example, the security and standards score 1416may be an alphabetical rating system (e.g. A, B, C, D, F). In furtherembodiments, the security and standards score 1416 may be highlighted toprovide a visual indication of the overall score. For example, red mayindicate a poor performance score, yellow a neutral performance score,and green a high performance score.

Finally, the comfort and health summary 1410 may include data related tothe comfort and health of the system. For example, the comfort andhealth summary 1410 may include data related to discharge airtemperature variations from the setpoint; duct static pressurevariations from the setpoint, and CO2 variations form the setpoint.However, additional data points are contemplated. The comfort and healthsummary 1410 may further include a comfort and health score 1418. Thecomfort and health score 1418 may provide a numerical score indicatingthe determined performance and savings associated with the system. Inone embodiment, the numerical score may be between one and ten, with tenrepresenting the best score for a system. However, other scoring schemaare also considered. For example, the comfort and health score 1418 maybe an alphabetical rating system (e.g. A, B, C, D, F). In furtherembodiments, the comfort and health score 1418 may be highlighted toprovide a visual indication of the overall score. For example, red mayindicate a poor performance score, yellow a neutral performance score,and green a high performance score.

Turning now to FIG. 15, a screen shot of the performance assessment tool500 illustrating a supervisory device performance assessment summary1500 is shown, according to some embodiments. Supervisory devices may bethose devices within the BMS responsible for controlling multipledevices or controllers throughout the system. The supervisory deviceperformance assessment summary 1500 may include a firmware versionssummary 1502. The firmware versions summary 1502 may provide datarelating to what version of firmware is running on the supervisorydevices in the system. The supervisory device performance assessmentsummary 1500 may further include a BMS control software compliancesummary 1504. For example, the BMS control software compliance summary1504 may indicate which version of the BMS control software is beingused by the supervisory devices. In one embodiment, the BMS controlsoftware is Johnson Control's Metasys software platform. However, otherBMS control software platforms are considered, such distributed controlplatforms (e.g. Verasys from Johnson Controls), a Peak softwareplatform, or a BCM software platform. The supervisory device performanceassessment summary 1500 may further include a supervisory deviceinformation summary 1506. The supervisory device information summary maypresent information to a user regarding general information related toeach of the supervisory devices in the system. For example, thesupervisory device information summary 506 may include the device name,the firmware version, which data trunks the supervisory device isconnected to, the number of controllers associated with the supervisorydevice, an object count, and/or a list of issues associated with eachsupervisory device. In one embodiment, the supervisory deviceinformation summary 506 may include more data or less data associatedwith each of the listed supervisory devices. For example, a user may beable to select what data should be shown for each supervisory device.The supervisory device information summary 506 may further highlightportions of the displayed data associated with an issue associated witha supervisory device. For example, the firmware version of supervisorydevice NAE55-0001 is shown as highlighted, as the firmware is of aversion which may have a security vulnerability.

Turning now to FIG. 16, a screen shot of the performance assessment tool500 illustrating a controller performance assessment summary 1600 isshown, according to some embodiments. Controllers may be those controldevices in the system that are not configured as supervisory devices,but still control one or more other devices within the system. Thecontroller performance assessment summary 1600 may include a controllerfirmware version summary 1602. The controller firmware version summary1602 may provide a summary of all the firmware versions being run on thecontrollers within the system. The controller performance assessmentsummary 1600 may further include a controller detailed informationreport 1604. The controller detailed information report 1604 may providea number of details for each individual controller listed. Example datamay include firmware versions, application information, data pointsassociated with the controller, controller equipment (e.g. whatequipment or devices are being controlled by the controller), and anyother issues. The prior list is for example purposes only, and it isconsidered that more or fewer details may be provided, as required. Insome embodiments, the user may be able to select what data should beshown for each controller. The controller detailed information report1604 may further highlight portions of the displayed data associatedwith an issue of a controller. For example, the firmware version ofcontroller NAE7v128 is shown as highlighted, with an accompanying issuein the issue column indicating that the firmware is at risk.

Turning now to FIG. 17, a screen shot of the performance assessment tool500 is shown illustrating a point summary 1700, according to someembodiments. The point summary 1700 may include a list of all the pointsin the system. In one embodiment, the point summary 1700 may group thedata points based on the type of data point. For example, the datapoints may be grouped as analog inputs (AI), analog outputs (AO), binaryinputs (BI) and binary outputs (BO). However, other data type points arefurther contemplated. Further, the types of points may be groupedaccording to the type of devise they are associated with. For example,the point types may be grouped as they related to AHUs, VAVs, FCUs,and/or other device types within the system.

Returning now to FIG. 13A, the process 1300 may generate a customerreport at process block 1318, or an internal report at process block1320. In one embodiment, reports generated at process blocks 1318, 1320may be PDF-style reports. The reports 1318, 1320 may contain similarinformation, but may be formatted differently depending on if they areto be presented to a customer or internally. For example, the customerfacing report generated at process block 1318 may summarize the overallhealth of the BMS system, and list any potential service opportunities.In contrast, the internal report generated at process block 1320 mayprovide an itemized list of potential service opportunities found, andprovide detailed information for performing the service. The reportsgenerated at process blocks 1318, 1320 may generally provide informationrelating to the current performance of the system, as well assuggestions to improve the performance. In some embodiments, the reportsgenerated at process blocks 1318, 1320 may be used as a benchmarkingtool to visualize optimization status of the BMS over a time period. Forexample, year over year. The reports generated at process blocks 1318,1320 may be based on the analysis results presented at process block1316. Example reports are provided below; however it is contemplatedthat the user 1302 may be able to generate customized reports as needed.In some embodiments, the user 1302 may be able to customize the datashown in the reports, display the data in different graphs or charts(e.g. spider graphs, candlestick charts, bar charts, pareto charts,etc.). In further embodiments, the reports may be configured to performstatistical analysis of the data provided, such as Monte Carlo, or bestfit analysis. In some embodiments, the user 1302 may be able to generatethe reports on the fly, using the performance assessment tool 500.

Turning now to FIG. 18, a performance and savings report 1800 is shown,according to some embodiments. The performance and savings report 1800may include various data related to the performance and savings for thesystem. As shown in FIG. 18, the report 1800 includes a schedulingportion 1802. The scheduling portion 1802 may provide a textual portionexplaining the current status of the scheduling, as well as potentialsavings that may be achieved by further scheduling additional portionsof the system. The scheduling portion 1802 may further provide graphicalillustrations showing the current status of the scheduling performed inthe system, as well as a graphical illustration showing the potentialsavings ranges that could be achieved by scheduling the remainingequipment in the system that is not currently scheduled. The performanceand savings report 1800 may further include an economizer portion 1804.The economizer portion 1804 may provide textual and visual indicationdescribing the current status of the current economization of thesystem, as well as expected savings associated with modifying theeconomization of components within the system.

Turning now to FIG. 19, a maintenance and reliability report 1900 isshown, according to some embodiments. The maintenance and reliabilityreport 1900 may include information related to various maintenanceand/or reliability issues within the system. For example, themaintenance and reliability report 1900 may include information relatedto dirty filters, chiller operating hours, unbound references,improperly addressed devices, missing critical trends, unacknowledgedalarms, and/or percentages or devices exceeding MSEA limitation.However, the above list is exemplary only, and other maintenance and/orreliability information is further contemplated.

Turning now to FIG. 20, a security and standards report 2000 is shown,according to some embodiments. The security and standards report 2000may include information related to various security and/or standardsinformation within the system. For example, the security and standardsreport 2000 may include information related to BMS control system (e.g.Metasys, Verasys, etc.) default usernames and password usages. This mayindicate that there may be a security issue due to the use of defaultsusernames and/or passwords. In further examples, the security andstandards report 2000 may include information related to the number ofusers with administrative privileges, the number of dormant accounts,firmware vulnerability, U/L listed devices, and point categorization(i.e. how are the data points classified.).

In some embodiments, more detailed reports may also be provided. Forexample, FIG. 21 illustrates a detailed scheduling report 2100. Thedetailed scheduling report 2100 may include data related to currentstatus of scheduled devices, as well as potential savings that may beachieved by scheduling additional devices. Further, the detailedscheduling report may include the existing scheduling status for eachcontroller in the systems. In other examples, the detailed schedulingreport may include the scheduling status for other devices in thesystem. In some examples, a user may be able to select whether to viewdevices with schedules or devices without schedules. Turning now to FIG.22, a detailed motor report 2200 is shown, according to someembodiments. The detailed motor report 2200 may include informationrelated to one or more motors throughout the system. The detailed motorreport 2200 may include data related to ideal operations of the motors.For example, the detailed motor report 2200 may provide ideal operationschemes for the motors, to reduce their operation below 100%. Further,the detailed motor report 2200 may include information related to eachof the controllers and their associated motors.

Turning now to FIG. 23, an air handling unit reset strategies report2300 may be generated. The air handling unit reset strategies report2300 may include information related to the reset strategies for anumber of air handling units in the system. In one example, the unitreset strategy may relate to duct static pressure resets or dischargeair temperature resets. However, other reset strategies arecontemplated. The air handling unit reset strategies report 2300 mayfurther include information related to each controller responsible forcontrolling the number of air handling units, and their implementedreset strategies, if any.

Turning now to FIG. 24, a 100% outdoor air handling unit report 2400 isshown, according to some embodiments. The 100% air handling unit report2400 may include information related to portions of the system whichrequire 100% outside air. For example, operating rooms and somelaboratories may require 100% of the air to be from the outside. The100% outdoor air handling unit report 2400 may provide informationrelated to the controllers for the areas set to use 100% outside air.This report can be used to determine if the areas currently using 100%outside air required to do so, thereby allowing a user or customer toquickly visualize potential savings by eliminating 100% outside air areawhen it is not required.

Turning now to FIG. 25, a dirty filter report 2500 is shown, accordingto some embodiments. The dirty filter report 2500 may provideinformation relating to filter statuses across the system. In someexamples, the controllers associated with the devices having the dirtyfilters are also listed along with any associated filters. Turning nowto FIG. 26, a detailed UL listed device report is shown, according tosome embodiments. The detailed UL listed device report may contain acomprehensive list of all the UL listed devices, such as those used forsmoke control, located within the system. Turning now to FIG. 27, adetailed firmware vulnerabilities report 2700 is shown, according tosome embodiments. The detailed firmware vulnerabilities report 2700 mayprovide a comprehensive list of all devices within the system which arenoted as having firmware vulnerabilities, such as having out of datefirmware. Finally, turning now to FIG. 28, a detailed economizer report2800 is shown, according to some embodiments. The detailed economizerreport 2800 may provide a detailed view of the current status ofeconomization of devices within the system. The detailed economizerreport 2800 may also provide information relating to potential savingsthat may be achieved by increasing the amount of devices performingeconomization, or modification of existing economization schemes. Thedetailed economizer report 2800 may further include a list of all thecontrollers associated with the devices that are currently economized,or are capable of being economized.

Returning now to FIG. 13A, once the reports have been generated atprocess blocks 1218, 1320, the project may be saved at process block1322. In one embodiment, the project is saved in the memory 508 of theperformance assessment tool 500. In other embodiments, the project issaved in the knowledgebase 540. Once the project has been saved, thegenerated customer reports may be presented to a customer at processblock 1324. Presenting the customer reports to the customer may includeproviding a digital copy to the customer. In other embodiments, a linkto view the report may be provided to the customer. In still furtherembodiments, the user 1302 may provide report to the clientelectronically (CD ROM, Flash Drive, etc.) or provide a hard copy.

At process block 1326, the user 1302 may use the generated internalreport to correct issues related to the system. For example, the process1300 may be used to provide a list of action items for increasing theperformance of the system. In one example, a service technician may runthe report to determine what maintenance is required. In otherembodiments, the process 1300 may be initiated after commissioning ofthe system, or when new components are added.

The user 1302 may optionally instruct the performance assessment tool500 to compare performance assessments. Turning now to FIG. 13B, aprocess 1350 for comparing performance assessments is shown, accordingto some embodiments. In one embodiment, the process 1350 is performedafter the process 1300, described above, completes the performanceassessment of the BMS. However, in other embodiments, a user may be ableto compare the two or more previously determined performanceassessments. For example, the user 1302 may wish to compare previouslysaved projects to determine how the system performance has changed overtime. At process block 1352 the user 1302 selects which projects tocompare. For example, the user 1302 may select the most recentlycompleted project and a project from one year prior for analysis. Inother examples, the user 1302 may select any two saved projects forcomparison. In some embodiments, the user 1302 may select more than twoprojects for comparison.

At process block 1354 the projects are compared. In one embodiment, theprojects are compared by comparing the performance scores associatedwith different features of the BMS. For example, the performance scoresassociated with the performance and savings, maintenance andreliability, security and standards, and/or comfort and health of theBMS may be compared. In other embodiments, other portions of the BMSperformance can be prepared. In one embodiment, the user 1302 may beable to select which performance aspects of the BMS system they wouldlike compared. In other embodiments, each of the performance aspects ofthe BMS system assessed in each project selected for comparison will becompared. In further embodiments, the inventory associated with theselected project may also be compared, as described in regards to FIG.11, above.

At process block 1356, an analysis is performed on the comparisonresults. The analysis may be performed by the system performance module512 of the performance assessment tool 500. The analysis may provideadditional analysis of the comparison results. For example, the analysismay determine metrics, such as improvements over time in performance. Inother embodiments, the analysis may further determine what changes haveoccurred to the BMS between the time of each of the compared projects,and provide additional information around the improvements, ordecreases, in performance associated with one or more changes made tothe BMS. For example, changes in inventory, firmware updates, etc.Further analysis may include analyzing the data to provide a graphicalrepresentation of the changes in the performance of the BMS. In stillfurther embodiments, the analysis may determine additional changes ormodifications to the BMS that could further improve the performance ofthe BMS. Once the analysis is completed, the differences between theprojects may be provided to the user at process block 1358. For example,the pure comparison results, along with the analysis performed atprocess block 1356. Finally, a performance comparison report may begenerated at process block 1360 to show the differences in theperformance of the system over time. In some embodiments, theperformance comparison report may include both the comparison results,as well as the analysis performed at process block 1356.

Turning now to FIG. 29, a performance comparison report 2900 is shown,according to some embodiments. The performance comparison report 2900may provide a comparison illustrating a performance assessment summaryof the system being analyzed at two or more time periods. For example,the performance comparison report 2900 may compare two performanceassessment summaries one year apart. Similar to the performanceassessment summary 1400 described above, the performance comparisonreport may include a comparative performance and savings score 2902, amaintenance and reliability score 2904, a security and standards score2906 and a comfort and health score 2908. Similar to above, these scores2902, 2904, 2906, 2908 may provide a numerical score indicating thecurrent determined performance scores for each of the above categories.In some examples, additional categories may also be presented to a userhaving a numerical score. In one embodiment, the numerical score may bebetween one and ten, with ten representing the best score for a system.However, other scoring schema are also considered. For example, thescores 2902, 2904, 2906, 2908 may be presented as an alphabetical ratingsystem (e.g. A, B, C, D, F). In further embodiments, the scores 2902,2904, 2906, 2908 may be highlighted to provide a visual indication ofthe overall score. For example, red may indicate a poor performancescore, yellow a neutral performance score, and green a high performancescore.

Additionally, each score 2902, 2904, 2906, 2908 may have a differenceindicator to indicate the change in the score over time. For example,the performance and savings score 2902, may have a performance andsavings difference indicator 2910. The performance and savingsdifferences indicator 2910 may be a positive or negative number wherethe performance and savings score 2902 is a numerical value. Forexample, if the performance and savings score 2902 has improved from ascore of five, to a score of six in the time period provided in thecomparison, the performance and savings difference indicator 2910 wouldbe one. However, if the performance and savings score 2902 has decreasedfrom a score of five to a score of four, the performance and savingsdifference indicator 2910 would be negative one. Similarly, if there isno change in the performance and savings score 2902, the performance andsavings difference indicator 2910 would be zero. Similarly, themaintenance and reliability score 2904 has a maintenance and reliabilitydifference indicator 2912, the security and standards score 2906 has asecurity and standards difference indicator 2914, and the comfort andhealth score 2908 has a comfort and health difference indicator 2916.

By illustrating the difference in performance and savings, maintenanceand reliability, security and standards, and comfort and health, theuser can quickly determine the impact of changes to a system over aperiod of time. In some instances, this can provide a useful tool tomonitor improvements made to a BMS system over time, and to easilydisplay and relay the information to other. Additionally, while theabove examples describe comparing performance of a given system overtime, it is contemplated that the performance assessment tool 500described above may further be able to provide similar comparisonsbetween different, but similar systems. For example, the performanceassessment tool 500 may be configured to compare the performance of aBMS system associated with one facility, with a BMS system associatedwith a similar facility. In some embodiments, the performance assessmenttool 500 may have access to the performance data for multiple BMSsystems in a variety of applications, such as factories, officebuilding, colleges or universities, and/or hospitals. The performancedata may be used to provide performance comparison reports, such asperformance comparison report 2900 described above. The performancecomparison reports may be used to benchmark different similar facilitiesagainst each other. In some embodiments, the results from thebenchmarked results can be used to generate performance scores fordifferent aspects of a BMS, such as those described above.

Turning now to FIG. 30, a feature assessment process 3000 is shown,according to some embodiments. A user 3002 may choose to create a newfeature assessment project at process block 3004, or open an existingassessment project at process block 3006. Once the feature assessmentproject has been selected, the performance assessment tool 500 mayreceive data from the BMS 526 via the communication interface 518. Insome embodiments, the performance assessment tool 500 may transmit arequest for data to the BMS 526 via the communication interface 518. Forexample, the performance assessment tool 500 may request dataspecifically related to one or more features of within the BMS 526. Inother examples, the performance assessment tool 500 may extract therequired data from data received from the BMS 526 via the communicationinterface 518. The data may be stored in one or more controllers withinthe BMS 526 capable of utilizing the features. Further, the systemfeatures module 514 may generate the instructions to retrieve the datafrom the BMS 526.

In a further embodiment, the performance assessment tool 500 may accessthe knowledgebase 540, and provide feature related data within theknowledgebase 540 to the performance assessment tool 500. The featurerelated data may include historical utilization data, typicalutilization data, potential savings data, etc. The potential savingsdata may be potential energy savings data, potential cost savings data,etc. In some embodiments, the potential savings data is determined basedon previous savings data gathered from previous installation of the oneor more features of the BMS. In other examples, general data, such asenergy costs provided by the Department of Energy, may be used toprovide potential savings data. In some embodiments, the feature relateddata includes data related to the BMS 526. In further embodiments, thefeature related data may include data related to the BMS 526, as well asother BMS systems. For example, the knowledgebase 540 may be a centralrepository for all BMS systems associated with a given entity (e.g.company, system provider, etc.). In other examples, the knowledgebase540 may be a central repository for BMS systems associated with multipleentities. Accordingly, the feature related data may be able to providedhistorical utilization data, typical utilization data, previouslymeasured savings data, or other like data, based on data provided mymultiple BMS systems of differing size and complexity. This can allowthe system features module 514 to benchmark the current utilization offeatures within the BMS 526 against other BMS systems across differentindustries, geographic locations, etc.

At process block 3010, the data is analyzed to determine a number offeature utilization attributes. In one embodiment, the data is analyzedby the system features module 514 of the performance assessment tool500. The system features module 514 may analyze data received from boththe BMS 526, as well as the knowledgebase 540. The feature utilizationattributes may be a usage history for one or more features. The featureutilization attributes may further be a listing of all controllersand/or devices within the system that current utilize one or moreavailable features, as well as a listing of all controllers and/ordevices within the BMS 526 that are not utilizing the one or morefeatures. Similarly the feature utilization attributes may be ananalysis of which systems and/or subsystems currently utilize one ormore available features. The feature utilization attributes may furtherinclude information relating to all of the systems, subsystems,controllers, and/or devices within the BMS 526 which are capable ofutilizing the one or more features.

At process block 3012 the system features module 514 may determine what,if any, features within the system are underutilized, or not utilized atall. The system features module 514 may analyze the feature utilizationattributes to determine which features may be underutilized. In someexamples, the system features modules 514 may determine that a featureis underutilized when the features has not been activated within theBMS. In other embodiments, the system features module 514 may determinethat a feature is underutilized when the feature is only activated in aportion of the BMS 526. In still further embodiments, the systemfeatures module 514 may determine a feature is underutilized if thepotential benefits of the feature are not being realized. The potentialbenefits may include energy savings, cost savings, efficiency increases,etc. In one embodiment, the system features module 514 evaluates thecurrent benefits being realized by the BMS 526, and compare the currentrealized benefits against similar BMS systems utilizing similar featuresto determine if the feature is underutilized. For example, the systemfeatures module 514 may analyze feature utilization data from othersimilar BMS systems provided by the knowledgebase 540, such as annualcost savings, equipment efficiencies, percent utilization withsub-systems of the BMS, etc. This information can then be used tocompare, or benchmark, the feature utilization of the BMS 526.

At process block 3014, the system features module 514 generates anassessment of the utilization of one or more features associated withthe BMS 526. In one embodiment, the assessment includes a listing ofunderutilized features associated with the BMS 526. The assessment mayfurther describe the benefit of each identified, underutilized feature.In some embodiments, the system feature module 514 what requirements arenecessary to implement a certain feature in the system. In oneembodiment, the system feature module 514 may determine the requirementsto implement the feature in the system based on the size of the system(e.g. the number of devices, data points, etc.). Further, the systemfeature module 514 may, via the performance assessment tool 500, providedata to the knowledgebase 540 regarding the determination of theutilization of features in the system. This data may be saved as featurerelated data which can be used in future feature utilizationassessments. In one embodiment, the assessment is provided to the user3002 via the user interface 520 of the performance assessment tool 500.In other embodiments, the assessment may be transmitted for display on amobile device, such as mobile device.

At process block 3016, a report is generated. In one embodiment, thereport may be a PDF-style report. The report may include a listing offeatures that are underutilized within the BMS 526. Example features mayinclude an optimal start feature, a Demand Limiting Load Rolling (DLLR)feature, a user views feature, a solar clock feature, a tailoredsummary, a BMS control system (e.g. Metasys, Verasys, etc.) userinterface feature, and other features, as applicable. Turning now toFIG. 31, an optimal start feature report 3100 is shown, according tosome embodiments. In one example, the optimal start feature may be anOptimal Start Stop (OSS) solution from Johnson controls. The OSSsolution is a fully engineered Metasys configuration tool designed toreduce the operating hours of constantly running equipment or equipmentoperating against a fixed time schedule. The OSS solution can adjustsystem start and stop times to meet a desired set point based onmultiple variables such as zone temperatures and outdoor air conditions.The OSS solution can be used to save energy, reduce runtime, extendequipment life, and/or reduce carbon output. The optimal start featurereport 3100 may provide information to the user regarding the potentialimpact of implementing the optimal start feature within the system.

Turning now to FIG. 32, a demand limiting load rolling (DLLR) report3200 is shown, according to some embodiments. The DLLR feature may beused to limit peak energy usage by monitoring the actual energy usage,comparing it to a user configured tariff structure, and then sheddingnon-critical loads to ensure the optimal usage by avoiding additionalcost. For example, demand limiting may be used to selectively turn offequipment, such as fans and lights, or to adjust set points to limitenergy use during periods of the day that are traditionally high-usage.Similarly, load rolling may continuously act to maintain a specifiedenergy reduction by shedding non-critical loads, which can help toreduce overall energy consumption. The DLLR report 3200 may provide abasic overview to the user 2902, and provide information relating to theimpact of implementing a DLLR feature in the system.

Turning now to FIG. 33, a user views report 3300 is shown, according tosome embodiments. The user views report 3300 may provide an assessmentof the current user interface views, and provide feedback regarding howto better implement the user views functionality. The user views featuremay allow any object in the system to be displayed, such as schedules,room temperatures, and graphics. In one embodiment, the user viewsfeature may allow for user specific views. Returning now to FIG. 30,once the reports have been generated at process block 3012, the reportscan be provided to a customer or other end user at process block 3014.

Turning now to FIG. 34, a riser assessment process 3400 is shown,according to some embodiments. The riser assessment process 3400 may beused to evaluate the current devices and controls in a system prior toand after an upgrade to the system. In one embodiment, the riserassessment process 3400 may be used to determine how to best upgrade asystem. A user 3402 may open an existing project at process block 3404.The existing hardware list is then provided at process block 3406. Inone embodiment, the process may provide the current riser diagram atprocess block 3408. The riser diagram may provide an overall schematicview of one or more sub-systems within the system. The riser diagram maythen be exported to a visualization program at process block 3410. Inone embodiment, the visualization program is Microsoft Visio. Theprocess 3400 may further provide a list of legacy devices at processblock 3412. The list of legacy devices may then be exported to thevisualization program at process block 3414. The process 3400 may alsoprovide an analysis of the counts at process block 3416. The analysis ofthe counts can then be used to generate an internal report at processblock 3418. At process block 3420 the internal report, legacy devicelist and riser diagram may be exported to a sales program for estimationof a cost to upgrade the existing system. At process block 3422 theupgrade may be performed. In one embodiment, the upgrade is physicallyperformed. In other embodiments, the upgrade is simulated. Once theupgrade has been performed, a new scan of the system can be performed atprocess block 3424. At process block 3426 the process 3400 may provide alist of any remaining legacy devices in the system. At process block3428 the process may generate the new riser diagram. At process block3430 the generated new riser diagram may be exported to thevisualization program. Finally, the exported riser diagram may beprovided to a customer for their records or review at process block3432.

Configuration of Exemplary Embodiments

The construction and arrangement of the systems and methods as shown inthe various exemplary embodiments are illustrative only. Although only afew embodiments have been described in detail in this disclosure, manymodifications are possible (e.g., variations in sizes, dimensions,structures, shapes and proportions of the various elements, values ofparameters, mounting arrangements, use of materials, colors,orientations, etc.). For example, the position of elements may bereversed or otherwise varied and the nature or number of discreteelements or positions may be altered or varied. Accordingly, all suchmodifications are intended to be included within the scope of thepresent disclosure. The order or sequence of any process or method stepsmay be varied or re-sequenced according to alternative embodiments.Other substitutions, modifications, changes, and omissions may be madein the design, operating conditions and arrangement of the exemplaryembodiments without departing from the scope of the present disclosure.

The present disclosure contemplates methods, systems and programproducts on any machine-readable media for accomplishing variousoperations. The embodiments of the present disclosure may be implementedusing existing computer processors, or by a special purpose computerprocessor for an appropriate system, incorporated for this or anotherpurpose, or by a hardwired system. Embodiments within the scope of thepresent disclosure include program products comprising machine-readablemedia for carrying or having machine-executable instructions or datastructures stored thereon. Such machine-readable media can be anyavailable media that can be accessed by a general purpose or specialpurpose computer or other machine with a processor. By way of example,such machine-readable media can comprise RAM, ROM, EPROM, EEPROM, CD-ROMor other optical disk storage, magnetic disk storage or other magneticstorage devices, or any other medium which can be used to carry or storedesired program code in the form of machine-executable instructions ordata structures and which can be accessed by a general purpose orspecial purpose computer or other machine with a processor. Combinationsof the above are also included within the scope of machine-readablemedia. Machine-executable instructions include, for example,instructions and data which cause a general purpose computer, specialpurpose computer, or special purpose processing machines to perform acertain function or group of functions.

Although the figures show a specific order of method steps, the order ofthe steps may differ from what is depicted. Also two or more steps maybe performed concurrently or with partial concurrence. Such variationwill depend on the software and hardware systems chosen and on designerchoice. All such variations are within the scope of the disclosure.Likewise, software implementations could be accomplished with standardprogramming techniques with rule based logic and other logic toaccomplish the various connection steps, processing steps, comparisonsteps and decision steps.

What is claimed is:
 1. A performance assessment device for evaluating abuilding management system (BMS) installed in a building, the devicecomprising: a communication interface configured to communicate with aBMS network; and a processing circuit configured to: receive performancedata related to the building via the communication interface; evaluatethe performance data related to the building to generate a performanceassessment for the building, the performance assessment comprising anindication of one or more HVAC devices that do not have an operatingschedule associated therewith and an indication of potential savingspredicted to result from configuring the operating schedule for the oneor more HVAC devices; and provide a user interface to a user that allowsthe user to view the performance assessment and perform an action toinitiate configuring the operating schedule for the one or more HVACdevices.
 2. The device of claim 1, wherein the performance assessmentfurther comprises one or more of a site information status, a criticalissues status, a corrective maintenance status, and a key tasks liststatus.
 3. The device of claim 2, wherein the site information statuscomprises an inventory of the building, the inventory of the buildingcomprising a list of servers, supervisory devices, controllers, and datapoints associated with the building.
 4. The device of claim 1, whereinthe processing circuit is further configured to request the performancedata related to the building from a BMS access device, the BMS accessdevice configured to scan the BMS installed in the building to collectthe requested data.
 5. The device of claim 1, wherein the processingcircuit is further configured to access a knowledgebase, theknowledgebase configured to store performance data associated with oneor more additional buildings.
 6. The device of claim 5, wherein theperformance data associated with the one or more additional buildingscomprises at least one of BMS specifications, physical plant schematics,riser diagrams, installed components, maintenance records, and servicecontracts.
 7. The device of claim 5, wherein the processing circuit isfurther configured to generate the performance assessment using datafrom the knowledgebase in addition to the performance data received viathe communication interface.
 8. The device of claim 1, wherein theperformance assessment further comprises a performance score, amaintenance score, and a security score associated with the building. 9.A method for assessing performance of a building management system (BMS)installed in a first building, the method performed by one or moreprocessors, the method comprising: scanning the BMS to retrieveperformance data related to the first building; accessing aknowledgebase to retrieve performance data related to a second building;analyzing the performance data related to the first building relative tothe performance data related to the second building to generate aperformance assessment for the first building, the performanceassessment comprising an indication of one or more HVAC devices that donot have an operating schedule associated therewith and an indication ofpotential savings predicted to result from configuring the operatingschedule for the one or more HVAC devices; and providing a userinterface to a user via a user device that allows the user to view theperformance assessment and perform an action to initiate configuring theoperating schedule for the one or more HVAC devices.
 10. The method ofclaim 9, wherein the performance assessment further comprises one ormore of a filter status, a motor current status, an active optimizationparameters status, and an air pressure values status.
 11. The method ofclaim 9, further comprising comparing the performance assessment to apreviously generated performance assessment for the first building. 12.The method of claim 9, wherein the user device is a smartphone, atablet, a laptop, or a personal computer.
 13. The method of claim 9,further comprising updating the knowledgebase with the performanceassessment.
 14. The method of claim 9, wherein the performanceassessment further comprises a performance score, a maintenance score,and a security score associated with the first building.
 15. A buildingmanagement system (BMS) comprising: a knowledgebase configured to storeBMS performance data associated with a plurality of buildings; and aperformance assessment tool configured to: receive performance datarelated to a first building from a network associated with the firstbuilding; receive performance data related to a second building from theknowledgebase; evaluate the performance data related to the firstbuilding relative to the performance data related to the second buildingto generate a performance assessment for the first building, theperformance assessment comprising an indication of one or more HVACdevices associated with the first building that do not have an operatingschedule associated therewith and an indication of potential savingspredicted to result from configuring the operating schedule for the oneor more HVAC devices associated with the first building; provide a userinterface to a user via a user device that allows the user to view theperformance assessment and perform an action to initiate configuring theoperating schedule for the one or more HVAC devices associated with thefirst building.
 16. The system of claim 15, wherein the performanceassessment further comprises a performance score, a maintenance score,and a security score associated with the first building.
 17. The systemof claim 15, wherein the performance assessment tool is furtherconfigured to compare the performance assessment to a previouslygenerated performance assessment for the first building.
 18. The systemof claim 16, wherein the maintenance score provides an indication ofreliability of equipment controlled by the BMS.
 19. The system of claim15, wherein the performance assessment tool is further configured todetermine a current inventory of the first building.
 20. The system ofclaim 19, wherein the current inventory comprises a listing of servers,supervisory devices, controllers, and data points associated with thefirst building.